Skip to content

Introduce nix flake - #81

Open
TureBentzin wants to merge 3 commits into
monal-im:masterfrom
TureBentzin:master
Open

Introduce nix flake#81
TureBentzin wants to merge 3 commits into
monal-im:masterfrom
TureBentzin:master

Conversation

@TureBentzin

Copy link
Copy Markdown

Nix is a powerful build system that is used by more people every day. I thought your project would benefit from a nix flake which adds a devshell for nix users and allows your packages to be build inside of the nix build system.

I tested all packages for functionality.

You can learn more about nix (if required) here: https://nixos.org/

@TureBentzin
TureBentzin marked this pull request as ready for review September 6, 2026 20:04
Comment thread README.md

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please do not add the nix deployment option in the README!

@Sobottasgithub Sobottasgithub left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The nix flake is fine but dont add the deployment options in the README. Im working with nix myself so i think it would make development for me more easy

@TureBentzin

TureBentzin commented Sep 8, 2026

Copy link
Copy Markdown
Author

Dear Sobottasgithub,

I initially prepared this response when your comment still asked whether a Nix flake was needed at all.

From my perspective, having the flake is useful because it provides a reproducible development environment and removes a significant amount of setup work for Nix/NixOS users. Without it, contributors using Nix would effectively have to recreate much of this environment themselves before being able to work on DebugTools conveniently. This also applies to users who just want to build packages from the DebugTools on NixOS (or with Nix).

Regarding the README, I also think documenting the supported build and development setup is generally good practice. That said, I understand your updated concern about the scope of the Nix-related documentation.

I’m happy to adjust the wording or reduce the section to focus primarily on the development environment rather than the deployment/package outputs. Feel free to suggest what scope you would prefer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants